Micro installation process for software packaging and distribution

ABSTRACT

The present invention discloses a software program that includes a first set of one or more compressed files and an executable file. The executable file can include a second set of one or more compressed files. The software program can be a self-executing program stored in a machine readable medium. Executing the software program can result in an automatic extraction of files contained within the first set and the second set of compressed files. In one embodiment, the software program can be an installation program, which includes a configuration file specifying settings to be applied during an installation process. The installation program can be dynamically constructed at a time an installation file is requested. The installation program can be a network lean file containing only those necessary components for a customized installation, which minimizes an amount of time and bandwidth expended when transferring the installation program over a network.

BACKGROUND

1. Field of the Invention

The present invention relates to the field of software distribution and,more particularly, to configurable and to a micro installation processfor software packaging and distribution.

2. Description of the Related Art

There are many incarnations of self-extracting executable installercreation programs which allow software makers to create customizedinstallable executables. However, these executables are staticallycreated, lack flexibility, and require complicated scripts. Changes tothe installer require the creators to reconstruct the installer, whichcan be a time consuming process. When multiple variants of the installerare necessary, it is not uncommon that a single monolithic installer,with all the software necessary for each configuration, is used.Installer generated installation files can be relatively large filesthat consume significant bandwidth when conveyed over a network and thatconsume significant computing resources when executed. Difficult to editscripts are needed to manage the installation process. This results ininstallers with large file sizes that have excessive softwarecomponents, which negatively affect performance and distribution.

When packaging software components for customized distribution andinstallation, it is often useful and necessary for users to make changesto suit special needs. For example, value added resellers may desire tobrand an installation and to add additional components other than thosethat are part of a distributed product. In another example, a corporateinformation technology (IT) administrator may desire to makeinstallation changes to tailor an installation to the company's needs,instead of being forced to make repetitive post-installation changeseach time a product is installed. A lack of ability to tailor currentinstallation routines has resulting in many IT departments creatingsoftware images of a model computer environment, then installing thisimage on similar computers. This practice saves time, but effectivelycircumvents a typical installation process of individual softwarepackages. Negatives resulting from this circumvention include havingimproper licensing information for software on imaged machines, havingimperfect matches between machine specific hardware and drivers, andreducing flexibility among various organization users by requiring useof a standard software configuration. Additionally, lack of ability totailor current installation results in packaging everything and as aresult produces a large network payload for distribution. For example,an eight megabytes software product could be distributed within as aseventy-five megabytes installation file.

Current installer programs generally result in a fixed deployableexecutable, which users, resellers, and distributors cannot easilymodify in a desired manner. Additionally, many software producersutilize in-house tools and/or third party software to create installablesoftware packages. To perform modifications, the users are forced to ownthe same installer tools, which is often infeasible and monetarilyprohibitive. This is assuming that the users wanting to modify theinstallable software packages even have access to package sourceartifacts that modifications can be made against. Additionally, many ofthe installer tools are platform specific, which results in problemsdeploying software across multiple platforms. It would be advantageousif a flexible and adaptable solution for a self-extracting executableinstaller were devised.

SUMMARY OF THE INVENTION

The present invention discloses a solution for creating and usingconfigurable and extensible self-extracting executables for softwaredistribution based on compressed archives. In the solution, a softwareprogram can include a self-extracting executable capable ofconcatenating to the executable one or more compressed archivescontaining software components. Creation of the executable can includethe use of system commands such as copy, cat, and the like. Theresultant executable can be directed by a configuration file included inthe executable. Additional compressed archives can be concatenatedthroughout the life cycle of the executable and the configuration filecan be similarly modified throughout the life cycle. Execution of theprogram can result in parsing the configuration file, if present, anduncompressing of all constituent compressed archives. Upondecompression, the executable can execute a command or program, such asan installation kickoff program.

Unlike traditional installation programs, those produced by the solutionare network lean and configurable. Network lean can be important insituations where a program or set of programs are to be deployed on alarge number of machines, such as on ten thousand machines belonging toa corporate network. The installation programs resulting from thedisclosed solution can include minimal installer overhead. Thesolution's installation programs also are high performance ones, sinceextraneous installer specific processes are minimized and processingresources are not consumed by an installer. Improved installationperformance can be especially important when deploying software onresource limited devices, such as mobile telephones, gaming platforms,and media players. Additionally, the programs necessary for creatingdeployable solutions or for modifying the same are very light-weight.The light weight installer can perform necessary functions from either acommand line or a GUI interface. The installer can easily be deployed ina standardized manner across multiple platforms.

The present invention can be implemented in accordance with numerousaspects consistent with the materials presented herein. One aspect ofthe present invention can include a software installation method thatincludes a step of creating a first installation archives. The firstinstallation archive can include at least one compressed file having anengrained directory structure for at least a first part of aninstallable software program. After the creation of the firstinstallation archive, a second installation archive can be created byadding at least one additional compressed file to the first installationarchives. The additional compressed file can also include an engraineddirectory structure for at least a second part of said installablesoftware program. The first installation archive and the secondinstallation archive can both be self-executing files. The secondinstallation archive can encapsulate the first installation archive andthe at least one additional compressed file. The second installationarchive can execute upon a target computing device. Executing the secondinstallation archive can result in decompressing the compressed filescontained in the first and second archives, which results in files beingadded to a storage space accessible by the target computing device,where the added files conform to the engrained directory structuresdefined by the first and second archives. After the second installationarchive is executed, the installable software program including a firstpart and the second part has been installed on the target computingdevice.

Another aspect of the present invention can include a method forpackaging and distributing software. The method can include a step ofreceiving a user request specifying a desired core software installationfile and a user selected set of optional configuration packages. A microinstall process archive can be dynamically created that includes a firstself executing file and zero or more additional self executing files.Each of the additional self executing files can represent a userselected optional configuration package for a software installation.Each of the self executing files can include a set of compressed fileshaving an engrained directory structure. The micro install processarchive can be conveyed to a requester. When the micro install processarchive is executed upon a target computing device, all compressed filescontained in the self executing files can be extracted to a storagespace of the target computing device. The engrained directory structurecan be preserved after extraction.

Still another aspect of the present invention can include a softwareprogram that includes a first set of one or more compressed files and anexecutable file. The executable file can include a second set of one ormore compressed files. The software program can be a self-executingprogram stored in a machine readable medium. Executing the softwareprogram can result in an automatic extraction of files contained withinthe first set and the second set of compressed files. In one embodiment,the software program can be an installation program, which includes aconfiguration file specifying settings to be applied during aninstallation process.

It should be noted that various aspects of the invention can beimplemented as a program for controlling computing equipment toimplement the functions described herein, or as a program for enablingcomputing equipment to perform processes corresponding to the stepsdisclosed herein. This program may be provided by storing the program ina magnetic disk, an optical disk, a semiconductor memory or any otherrecording medium. The program can also be provided as a digitallyencoded signal conveyed via a carrier wave. The described program can bea single program or can be implemented as multiple subprograms, each ofwhich interact within a single computing device or interact in adistributed fashion across a network space.

BRIEF DESCRIPTION OF THE DRAWINGS

There are shown in the drawings, embodiments which are presentlypreferred, it being understood, however, that the invention is notlimited to the precise arrangements and instrumentalities shown.

FIG. 1 is a schematic diagram illustrating a system for a highperformance, network lean and configurable software installationsolution in accordance with an embodiment of the inventive arrangementsdisclosed herein.

FIG. 2 is a schematic diagram illustrating a set of scenarios in whichimage archive instances, such as MIP archive instances, are created anddeployed in accordance with an embodiment of inventive arrangementsdisclosed herein.

FIG. 3 is a flowchart diagram illustrating a method for the creation ofan image archive, such as a MIP archive, in accordance with anembodiment of the inventive arrangements disclosed herein.

FIG. 4 is a flowchart diagram illustrating a method for utilizing animage archive, such as a MIP archive, in accordance with an embodimentof inventive arrangements disclosed herein.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic diagram illustrating a system 100 for a highperformance, network lean and configurable software installationsolution in accordance with an embodiment of the inventive arrangementsdisclosed herein. System 100 creates, deploys, and executes a MicroInstall Process (MIP) archive 130. The MIP archive 130 can be aself-executing compressed file having an ability to rapidly decompressitself. The MIP 130 can include executable code 142, a configurationfile 144, and a number of compressed archive files 146. A MIP archiveinstance 130 can be modified to add new compressed archives 146 and/orto alter the configuration file 144.

Additionally, a MIP archive 130 can be nested within other MIP archives130. When a parent archive 130 is executed, all child archives 130 alsoexecute, which results in all included compressed files 146 beingextracted regardless of what level of nesting they are contained within.The nesting ability permits a series of MIP archives 130 to beconstructed that include a core software installation component (in onearchive 130) and a set of optional components (in other archives 130)for a specific installation instance or client. MIP archives 130 can bedynamically or statically created.

As shown, a computing device 110 can utilize a MIP creation application112 to create a MIP archive 130 that includes one or more files 114 thatare packaged in a compressed form for deployment and installation uponone or more computing devices 120. Files 114 can include compressedarchives 146, configuration files 144, and the like. Once received bycomputing device 120, optional modification of MIP archive 130 canoccur. For example, a command line interface 126 can be used to addadditional compressed files to the archive 146. Executing the resultantself-extracting executable can invoke an installation process onprocessor 122 resulting in installed application 124.

Configuration file 144 can affect the execution of MIP archive instance140, such as dictating process priority, resource usage, program/commandexecution, and the like. On computing devices with limited resources,configuration file 144 can be used to direct the execution processwithin the device tolerances. Configuration file 144 can control programexecution based on the degree of success or failure of the executablecode 142. For example, configuration file 144 can indicate a clean upprocess that can be invoked when failure to uncompress a componentoccurs. In the event of a successful extraction of components, aconfiguration file 144 entry can indicate the appropriateprogram/command to execute. In one embodiment, configuration file 144can be a text file appended to the end of a MIP archive instance.Configuration file 144 can include a text file, XML file, YAML file,binary file, and the like.

Compressed archives 146 can maintain the original directory structureafter concatenation into the MIP archive instance 140. MIP archiveinstance 140 can store compressed archives 146 without requiringadditional data structures. As a result, compressed archives 146 can beeasily concatenated without modification to the MIP archive instance 140via a copy system command. Compressed archives 146 can be a filegenerated with any of a variety of different compression technologies.For example, the compressed archive 146 can be in a PKZIP, 7ZIP, RAR,GZIP, BZIP, or other compression format. In one embodiment, compressedarchives 146 can be homogenous in nature containing only one type ofcompressed archives. In another embodiment, compressed archives 146 canbe a one of multiple compressed formats. Further, compressed files canbe stand-alone files able to be uncompressed by themselves or can be oneof a set of component archived files, which must be joined to create amaster compressed file, which can be decompressed. (i.e., componentfiles—file.001, file.002, file.003, etc. can be joined to createfile.archive, which is a master compressed file.) Even after archive 130has been initially created and conveyed, additional files and/orconfiguration details can be added, which is shown by command lineinterface 126.

FIG. 2 is a schematic diagram illustrating a set of scenarios 210, 240in which image archive instances, such as MIP archive instances, arecreated and deployed in accordance with an embodiment of inventivearrangements disclosed herein. Scenarios 210, 240 can be performed inthe context of system 100. In each scenario 210, 240, a MIP archive 236,242 can facilitate remote software distribution and installation. Itshould be appreciated that modifications can occur to the MIP archive236 between it's creation by server 230 and it's installation at client211.

In scenario 210, a server 230 can distribute MIP archive 236 to client211 via network 220. The MIP archive 236 can be of arbitrary complexity.For purposes of scenario 210, MIP archive 236 can contain TIVOLIsoftware components, which are to be installed in client 211. The MIParchive 236 can contain software agents and libraries. Server 230 cancreate MIP archive 236 using application 234. In one embodiment,application 234 can be a command line interface (used in the example), agraphic user interface, a voice interface, or any other interface type.

A system command, such as cat, can be entered in the command lineinterface to create the MIP archive 236 from compressed files stored indata store 232. The created MIP archive 236 can be a self-extractingexecutable. A simplicity with which the MIP archive 236 is able to becreated can encourage a creation of customized packages containing aminimal amount of unnecessary overhead, which are ideally suited forresource efficient network deployments. For example, the MIP archiveinstance 236 can include JAVA runtime environment components and twoTIVOLI agents in a self-extracting executable. It is possible todynamically create a MIP archive 236 at runtime, which can be customizedfor a specific client 211 need. This need can be determined from manualuser specifications and/or by automatically querying a presentconfiguration of client 211. For example, client 211 can convey platformand installed package information specific to itself to server 230,which determines which components of a solution are needed for theclient. Application 234 can then dynamically package these components inarchive 236. Once created, MIP archive 236 can be conveyed to client 211for usage or further modification as shown in scenario 240.

In scenario 240, client 241 can modify MIP archive 236 to producemultiple variants 242 of the MIP archive 236 for usage on clients260-264. Modification of MIP archive 236 can be achieved usingapplication 244 as shown. As shown in application 244, differentversions of a software installation package (e.g., debank) can becreated by specifying unique configuration files (config 1-3) anddestinations (debank 1-3). Once multiple MIP archive variants 242 havebeen created, the variants 242 can be deployed over network 250 and canbe distributed to clients 260-264. Each variant 242 received by eachclient 260-264 can be specifically tailored to that client 260-264 orcan be tailored for a group of clients representing a particular clientplatform or configuration.

For example, client 260 can be a mobile computing device containingunique directory structures. Debank1 can be configured to install TIVOLIsoftware specific to the directory structure of the mobile computingdevice. In another instance, client 262 can be a desktop computer thatrequires additional library components for software installation, whichcan be included into a received archive prior to distribution. Client264 can be desktop computer having a different operating system thanclient 262.

In one embodiment, the client 241 that creates the MIP archive variants242 can be considered an installation server, which can be clustered(e.g., implemented as server 1, server 2, server 3, . . . server n) asdesired. For example, client 260 can be part of a set of clients thatcommunicate with server 1; client 262 can be part of a set of clientsconfigured to communicate with server 2; client 264 can be part of a setof clients configured to communicate with server 3; and so forth.Distributing a number of clients 260-264 across a set of servers canimprove scalability concerns in situations involving a large number(e.g., four hundred) of clients 260-264.

As shown herein, data store 232 can be physically implemented within anytype of hardware including, but not limited to, a magnetic disk, anoptical disk, a semiconductor memory, a digitally encoded plasticmemory, a holographic memory, or any other recording medium. The datastore 232 can be stand-alone storage units as well as a storage unitformed from a plurality of physical devices, which may be remotelylocated from one another. Additionally, information can be stored withinthe data store 232 in a variety of manners. For example, information canbe stored within a database structure or can be stored within one ormore files of a file storage system, where each file may or may not beindexed for information searching purposes.

Networks 220, 250 can include any hardware/software/and firmwarenecessary to convey digital content encoded within carrier waves.Content can be contained within analog or digital signals and conveyedthrough data or voice channels and can be conveyed over a personal areanetwork (PAN) or a wide area network (WAN). The networks 220, 250 caninclude local components and data pathways necessary for communicationsto be exchanged among computing device components and between integrateddevice components and peripheral devices. The networks 220, 250 can alsoinclude network equipment, such as routers, data lines, hubs, andintermediary servers which together form a packet-based network, such asthe Internet or an intranet. The networks 220, 250 can further includecircuit-based communication components and mobile communicationcomponents, such as telephony switches, modems, cellular communicationtowers, and the like. The networks 220, 250 can include line basedand/or wireless communication pathways.

FIG. 3 is a flowchart diagram illustrating a method 300 for the creationof an image archive, such as a MIP archive, in accordance with anembodiment of the inventive arrangements disclosed herein. The method300 can be performed in the context of system 100 or any similar system.The created archive can be used for deploying and installing software.Contents of the archive can include compressed files, configurationfiles, and the like.

The method can begin in step 305 where a set of files is identified tobe included in an archive instance. In step 310, a command can beexecuted to concatenate a set of compressed files into the archiveinstance. If files are initially uncompressed, an optional additionalstep of compressing the files can occur after step 305 and before step310. In step 315, if there are more compressed files to be included, themethod can return to step 305, else continue to step 320. In step 320,the archive instance can be deployed and distributed. In step 325, anoptional customized configuration of the archive instance can occur.Custom configuration can include concatenation of additional compressedfiles, addition of configuration files, and the like. Customization ofthe archive instance can occur after it is initially deployed by a user,distributor, or other entity. In step 330, the archive instance can beused during an installation process.

FIG. 4 is a flowchart diagram illustrating a method 400 for utilizing animage archive, such as a MIP archive, in accordance with an embodimentof inventive arrangements disclosed herein. The method 400 can beperformed in the context of system 100 or any similar system. The imagearchive of method 400 can be created and deployed using method 300.

The method 400 can begin in step 405 where a self-extracting executablearchive instance is executed. In step 410, the archive instance canexecute and can unpack each compressed file contained in the archiveinstance. For instance, the archive can be opened and read to determinewhich, if any, compressed files are included in the archive instance. Inone embodiment, one or more magic numbers can be included in the archiveinstance. Magic numbers implement strongly typed data and are a form ofin-band signaling to the controlling program that reads the data type(s)at program run-time. Detecting such constants in files is a simple,effective, and flexible way of distinguishing between many file formats.The unpacking process of step 410 can handle any included file having amagic number for a format, which adds to the solution's flexibility.Each compressed file included in the archive can have a known size asdefined by an associated compressed file format. Unpacking of thearchive can iteratively occur until no unprocessed files and no magicnumbers are found. Additionally, during unpacking, an optionalconfiguration file, which can be a flat text file, can be identified andcan be extracted from the archives. It should be understood that otherforms of metadata besides magic numbers can also be used, and that theinvention is not to be construed as limited in this regard.

After the archive instance is unpacked, the method can proceed to step415. In step 415, if a configuration file exists in the archiveinstance, the method can proceed to step 420, else jump to step 430. Instep 420 the configuration file, which can be a text file or other filefrom which content is able to be extracted, can be opened and parsed. Instep 425, the executable can executes a specified program/command in afashion specified by the configuration file. In step 435, one or moreapplications can be installed as a result of the executedprogram/command. After applications are installed, temporary filesgenerated during the installation can be optionally deleted, as can theimage archive file itself.

The present invention may be realized in hardware, software or acombination of hardware and software. The present invention may berealized in a centralized fashion in one computer system or in adistributed fashion where different elements are spread across severalinterconnected computer systems. Any kind of computer system or otherapparatus adapted for a carrying out methods described herein is suited.A typical combination of hardware and software may be a general purposecomputer system with a computer program that, when being loaded andexecuted, controls the computer system such that it carries out themethods described herein.

The present invention also may be embedded in a computer programproduct, which comprises all the features enabling the implementation ofthe methods described herein, and which when loaded in a computer systemis able to carry out these methods. Computer program in the presentcontext means any expression, in any language, code or notation, of aset of instructions intended to cause a system having an informationprocessing capability to perform a particular function either directlyor after either or both of the following: a) conversion to anotherlanguage, code or notation; b) reproduction in a different materialform.

What is claimed is:
 1. A software installation method comprising: creating a first installation archive comprising at least one compressed file, wherein said at least one compressed file has an engrained directory structure for at least a first part of an installable software program; after the creation of the first installation archive, creating a second installation archive by adding at least one additional compressed file to the first installation archive, wherein said at least one additional compressed file has an engrained directory structure for at least a second part of said installable software program, wherein said first installation archive and said second installation archive are both self-executing files; executing said second installation archive upon a target computing device, wherein said executing step comprises: decompressing said at least one additional compressed file in a storage space accessible by said target computing device, wherein said decompressing results in an expansion of said at least a second part said expansion having said engrained directory structure; and decompressing said at least one compressed file in a storage space accessible by said target computing device, wherein said decompressing results in an expansion of said at least a first part of said expansion having said engrained directory structure, wherein after said executing step, said installable software program comprising said at least a first part and said at least a second part has been installed on said target computing device.
 2. The method of claim 1, wherein said second installation archive encapsulates the first installation archive and the at least one additional compressed file.
 3. The method of claim 2, wherein the first installation archive is unmodified when encapsulated within said second installation archive.
 4. The method of claim 3, wherein said second installation archive comprises a configuration file, said executing step further comprising: reading installation details from said configuration file; and performing said decompressing steps in accordance with said installation details.
 5. The method of claim 1, wherein said at least a second part comprises an optional component of said installable software program not needed by every target computing device, said method further comprising: executing said first installation archive upon a second target computing device, wherein said executing step comprises: decompressing said at least one compressed file in a storage space accessible by said second target computing device, wherein said decompressing results in an expansion of said at least a first part, said expansion having said engrained directory structure of said at least a first part, wherein after said executing step, said installable software program comprising said at least a first part has been installed on said second target computing device.
 6. The method of claim 5, wherein said at least a second part comprises an optional component of said installable software program needed for a first computing platform, wherein said target computing device conforms to standards of said first computing platform, said method further comprising: creating a third installation archive by adding at least one different compressed file to the first installation archive, wherein said at least one different compressed file includes an engrained directory structure for at least a different part of said installable software program, wherein said third installation archive is a self-executing file that encapsulates the first installation archive and the at least one different compressed file, wherein the first installation archive is unmodified when encapsulated within said third installation archive; executing said third installation archive upon a different target computing device, said executing step comprising: decompressing said at least one different compressed file in a storage space accessible by said different target computing device, wherein said decompressing results in an expansion of said at least a different part, said expansion having said engrained directory structure of said at least a different part; and decompressing said at least one compressed file in a storage space accessible by said target computing device, wherein said decompressing results in an expansion of said at least a first part of said expansion having said engrained directory structure of said at least a first part, wherein after the step of executing said third installation archive, said installable software program comprising said at least a first part and said at least a different part has been installed on said different target computing device.
 7. The method of claim 1, wherein said step of creating the first installation archive results from processing a first operating system command, and wherein said step of creating the second installation archive results from processing a second operating system command.
 8. The method of claim 7, wherein the first operating system command and the second operating system command are standard operating system commands, each receiving at least one parameter specific to creating a related archive file.
 9. The method of claim 8, wherein said first operating system command and the second operating system command are entered by a user via a command line interface.
 10. The method of claim 1, wherein said steps of claim 1 are performed by at least one machine in accordance with at least one computer program stored in a non-transitory computer readable media, said computer programming having a plurality of code sections that are executable by the at least one machine.
 11. A method for packaging and distributing software comprising: receiving a user request specifying a desired core software installation file and a user selected set of optional configuration packages for a software installation; dynamically creating a micro install process archive comprising a first self executing file representing the core software installation file and comprising a plurality of additionally self executing files, one for each of the user selected optional configuration packages, wherein each of the self-executing files comprise a set of compressed files having an engrained directory structure, wherein the first self executing file and each of the additional self executing files are micro install process archive files, and wherein the dynamically creating step utilizes a standard operating system command that includes a plurality of parameters specific to creating the micro install process archive, wherein the plurality of parameters comprise a parameter for the first self extracting executable and an additional parameter for each of the additional self extracting executables; and conveying the micro install process archive to a requestor, wherein when the micro install process archive is executed upon a target computing device, all compressed files contained in the self executing files are extracted to a storage space of the target computing device while the engrained directory structure is preserved after extraction.
 12. The method of claim 11, wherein the micro install process archive is referable to as an original micro install process archive, said method further comprising: the requestor creating a new micro install process archive comprising said a set of compressed files and said original micro install process archive, wherein when the new micro install process archive is executed upon a target computing device, all compressed files contained in the self executing files including the set of compressed files of the new micro install process archive and those contained in the original micro install process archive are extracted to a storage space of the target computing device.
 13. A computer program product comprising: one or more computer-readable, non-transitory media; program instructions, stored on at least one of the one or more storage mediums, to create a first installation archive comprising at least one compressed file, wherein said at least one compressed file has an engrained directory structure for at least a first part of an installable software program; program instructions, stored on at least one of the one or more storage mediums, to, after the creation of the first installation archive, create a second installation archive by adding at least one additional compressed file to the first installation archive, wherein said at least one additional compressed file has an engrained directory structure for at least a second part of said installable software program, wherein said first installation archive and said second installation archive are both self-executing files; program instructions, stored on at least one of the one or more storage mediums, to execute said second installation archive upon a target computing device, wherein said executing step comprises: decompressing said at least one additional compressed file in a storage space accessible by said target computing device, wherein said decompressing results in an expansion of said at least a second part said expansion having said engrained directory structure; and decompressing said at least one compressed file in a storage space accessible by said target computing device, wherein said decompressing results in an expansion of said at least a first part of said expansion having said engrained directory structure, wherein after said executing step, said installable software program comprising said at least a first part and said at least a second part has been installed on said target computing device.
 14. The computer program product of claim 13, wherein said second installation archive encapsulates the first installation archive and the at least one additional compressed file.
 15. The computer program product of claim 14, wherein the first installation archive is unmodified when encapsulated within said second installation archive.
 16. The computer program product of claim 15, wherein said second installation archive comprises a configuration file, said executing step further comprising: reading installation details from said configuration file; and performing said decompressing steps in accordance with said installation details.
 17. The computer program product of claim 13, wherein said at least a second part comprises an optional component of said installable software program not needed by every target computing device, said computer program product further comprising: program instructions, stored on at least one of the one or more storage mediums, to execute said first installation archive upon a second target computing device, wherein said executing step comprises: decompressing said at least one compressed file in a storage space accessible by said second target computing device, wherein said decompressing results in an expansion of said at least a first part, said expansion having said engrained directory structure of said at least a first part, wherein after said executing step, said installable software program comprising said at least a first part has been installed on said second target computing device. 